• pfSense has detected a crash report or programming bug

    17
    0 Votes
    17 Posts
    2k Views
    E
    @stephenw10 We will try to find out. Thank you very much for your effort.
  • PHP Fatal Error: Type: 1

    Locked Moved
    6
    1 Votes
    6 Posts
    829 Views
    stephenw10S
    Ok, let's stick to the other thread: https://forum.netgate.com/topic/184197
  • Monitoring outgoing traffic

    9
    0 Votes
    9 Posts
    2k Views
    P
    @michmoor That's a really nice looking flow chart/graph. Is that something you have as a plugin on pfSense? I've been looking for a way to get that for a long time. I too agree with your statements on NtopNG being useless for anything other than realtime flows.
  • No internet after upgrading to 2.7.1

    Locked
    3
    0 Votes
    3 Posts
    300 Views
    stephenw10S
    Locking this in favour of: https://forum.netgate.com/topic/184207
  • Authentication Servers Microsoft 2022 AD + PfSense 2.7.0 - SSL

    6
    0 Votes
    6 Posts
    2k Views
    L
    Hello, Sorry about the delay. In fact the problem did not come from the configuration but simply from a DNS problem. I hadn’t paid attention, but the ping test was coming back to me from the IPs which does not concern my Network. The domain I thought was not used on the web is used. To make a test I tried to clamp PFSENSE so that it only gets my DNS from the AD without success. I changed the name of my domain and this time I made sure it was mine. Now it works out. thank you for your help.
  • SSL termination, traffic forwarded to varnish cache

    6
    0 Votes
    6 Posts
    690 Views
    L
    @stephenw10 said in SSL termination, traffic forwarded to varnish cache: I would expect that work yes. There any many people using HAProxy on pfSense pretty much exactly like that. Just wondered if I was overlooking something or maybe someone had written a nice article on putting this together. Thanks for your input folks.
  • Initial config blocks on WAN by default?

    2
    0 Votes
    2 Posts
    146 Views
    stephenw10S
    Everything is blocked by default incoming on WAN.
  • 23.09 Local NTP server "unrechable" (worked with 23.05.1)

    20
    0 Votes
    20 Posts
    2k Views
    C
    @johnpoz Thanks for your ongoing support! Not saying it's something wrong generally in 23.09 but at least something specific :-) Either in combination with my NTP server or something went wrong during the upgrade. Went back to 23.05.01 and everything is OK again [image: 1700388875485-bildschirmfoto-2023-11-19-um-11.01.37.png] [image: 1700388884603-bildschirmfoto-2023-11-19-um-11.01.52.png] After being back to 23.09 same as before... The flag "u" and "s" appears randomly or changes after some time, currently it is set to "u": [image: 1700389038112-bildschirmfoto-2023-11-19-um-11.16.09.png]
  • 1 Votes
    9 Posts
    1k Views
    Z
    I just ran into a headache/nightmare trying to downgrade. I was utilizing the AT&T bypass (WAN Connectivity with 802.1X Authentication Bridging and VLAN 0 PCP Tagging). I also had a hard time using a backup to restore from... For whatever reason if I redid the basic configuration at least back to the LAN being my previous IP address AND THEN did the restore it worked. But I then had to troubleshoot why I didn't have WAN access which was due to the MAC spoofing needing to be undone... Very inconvenient from the Plus license changes...
  • Lab and production firewalls sharing same Netgate Device IDs - dangerous?

    2
    0 Votes
    2 Posts
    218 Views
    G
    @Gcon FYI I sorted this out with Netgate support. cheers.
  • 6100er crash dump config import from NUC

    2
    0 Votes
    2 Posts
    237 Views
    stephenw10S
    Looks like this: https://redmine.pfsense.org/issues/14431 You have a number of interfaces that could apply to but I'd guess it's pppoe0. Do you have IPv6 enabled on that? On any other dynamic interface types? Steve
  • Analyzer for pfSense logs

    1
    0 Votes
    1 Posts
    149 Views
    No one has replied
  • easyrule stopped working after upgrading from 23.05 to 23.09

    Moved
    9
    0 Votes
    9 Posts
    838 Views
    D
    @stephenw10 A clean reinstall fixed the easyrule issues. All working fine now.
  • pfsense+ latest update Netgate 4100max

    11
    0 Votes
    11 Posts
    1k Views
    S
    @JuneKlein the serial port is listed in device manager but may not be com3. There is a reset procedure for this model: https://docs.netgate.com/pfsense/en/latest/solutions/netgate-4100/factory-reset.html
  • PFsense cannot ping on a new connection?

    11
    0 Votes
    11 Posts
    957 Views
    E
    @stephenw10 Bless you! Have a lovely day.
  • Auto Configuration Backup times are off

    8
    0 Votes
    8 Posts
    789 Views
    stephenw10S
    Yup, rechecking I think I see the issue. The server timestamps changed when it was moved to new infrastructure so this is no longer true: https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/services_acb.php#L71 Setting that to UTC shows the correct times for me. Asked our admins how they want to handle it. I imagine correcting the server timezone will fix this but we shall see. Steve https://redmine.pfsense.org/issues/15005
  • HA Proxy using HTTP with backend - Not configured for this

    2
    0 Votes
    2 Posts
    163 Views
    M
    FIXED. All i did was remove backend and frontend configuration and re-added it. Working fine. pcaps now show TLS communication with backend. Definitely a bug. Trying to reproduce so i can open a redmine but so far i cant.
  • 0 Votes
    16 Posts
    1k Views
    Yet_learningPFSenseY
    @Gertjan My screen looks a little different, but I set it up this way and completed successfully. The 1dot~ address is the one I was trying to get from here. It seems it was actually a different one... https://blog.cloudflare.com/ja-jp/enable-private-dns-with-1-1-1-1-on-android-9-pie-ja-jp/ ! alt text
  • Service Watchdog and Kea DHCP Server (kea-dhcp4)

    5
    0 Votes
    5 Posts
    657 Views
    QinnQ
    @stephenw10 said in Service Watchdog and Kea DHCP Server (kea-dhcp4): I understand. I'm just pointing out that, in general, you should not need to use the the service watchdog except when debugging some issue. So I was wondering if you had enabled it because Kea (or ISC dhcpd) was stopping unexpectedly. @stephenw10 No, I enabled Service Watchdog, because very occasionally (I am a beta tester for pfBlockerNG develop) a service stops and as a courtesy to users, it will bring it up again and send me mail, so I can check out the cause.
  • 0 Votes
    4 Posts
    445 Views
    stephenw10S
    Yup also see your other identical question: https://forum.netgate.com/post/1136501 You must use block rules for local subnet and any for the destination in pass rules. Or you can use 'not local' as a destination but it's generally better to avoid that. Steve
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.